Skip to content

reduce size of openmesh by excluding these from autoupdater-wifi-fallback #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: v2025.1.x
Choose a base branch
from

Conversation

maurerle
Copy link
Member

eventually this is enough - otherwise we have to declare the openmesh devices as tiny or something..

@maurerle maurerle force-pushed the fix_openmesh_firmware_size branch from 83744ce to cc211a2 Compare July 20, 2024 09:45
@maurerle
Copy link
Member Author

maurerle commented Aug 9, 2024

this is said to still not work by @Djfe

Kernel passt super so (0,89% des letzten erase-blocks ist voll, das hält hoffentlich für alle Kernelupdates von 2023.2)
rootfs ist 0.148MiB zu groß und muss dafür einen neuen erase-block anfangen. (ca. 60% eines flashblocks (256k) belegt das)
ff-web-ap-timer, web-private-wifi wären so Kandidaten, die man noch streichen könnte

@maurerle maurerle force-pushed the fix_openmesh_firmware_size branch from cc211a2 to 7d1d9d1 Compare July 3, 2025 23:06
@maurerle maurerle changed the base branch from v2023.2.x to v2025.1.x July 3, 2025 23:07
@maurerle
Copy link
Member Author

maurerle commented Jul 3, 2025

This should be checked with the image size checker from gluon main using:

./gluon-build/contrib/check-image-size.py --github-actions --overhead 256 output/meta/openwrt-profiles/*

@Djfe
Copy link
Member

Djfe commented Jul 3, 2025

I'm pretty certain this needs overhead 5x256 aka 1280 because these have flash chips with 256KiB blocksize

I don't understand how Overhead 256/5 = 51.2 (KiB) equals a blocksize tbh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants